Properly encode content-disposition header #31
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Fixes: #2
This is a port of zendframework/zend-mail#251 to this repository per zendframework/zend-mail#251 (comment).
When using UTF-8 encoding, this codebase was producing a header being of
Content-Disposition: =?utf-8?Q?inline?=
which is not interpreted properly by Thunderbird nor Microsoft Outlook. This pull request introduces specific handling of this header, so thatinline
will never be encoded as UTF-8 and therefore cannot be misinterpreted by some user agents.This is a proper fix for magento/magento2#25076. The work-around applied there was to no longer set a
content-disposition
header.